Devices, methods, and systems for hands free facility status alerts

ABSTRACT

Devices, methods, and systems for hands free facility status alerts are described herein. One system includes a computing device for hands free building automation notifications, comprising a memory and a processor to execute executable instructions stored in the memory to: receive a notification of an event from a building automation system, modify the notification to include only pre-defined attributes of the notification that are displayable on a user interface of a wearable device, and transmit the modified notification to the wearable device.

This is a continuation of co-pending U.S. patent application Ser. No.17/147,175, filed Jan. 12, 2021, which is a continuation of U.S. patentapplication Ser. No. 15/168,860, filed May 31, 2016, now U.S. Pat. No.10,911,255, both of which are incorporated herein by reference.

TECHNICAL FIELD

The present disclosure relates to devices, methods, and systems forhands free facility status alerts.

BACKGROUND

Building automation systems can be complex distributed systems. Forexample, a building automation system can include many different piecesof equipment. As a specific example, a building automation system caninclude different pieces of heating, ventilation, and air-conditioning(HVAC) equipment as well as other equipment such as sensors, operatingpanels, controllers, actuators, etc.

The different pieces of equipment included in a building automationsystem can generate alarms that can notify a user, such as a buildingmanager, of abnormalities in the building automation system. Forexample, a piece of equipment included in the building automationsystem, such as a piece of HVAC equipment, may generate an alarm inresponse to a fault in the HVAC equipment. The alarm may be sent to amobile device associated with the user by the building automationsystem.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an example of a system for hands free facility status alertsaccording to one or more embodiments of the present disclosure.

FIG. 2 is an example of a display for hands free facility status alertsaccording to one or more embodiments of the present disclosure.

FIG. 3 is an example of a display for hands free facility status alertsaccording to one or more embodiments of the present disclosure.

FIG. 4 is an example of a display for hands free facility status alertsaccording to one or more embodiments of the present disclosure.

FIG. 5 is an example of a display for hands free facility status alertsaccording to one or more embodiments of the present disclosure.

FIG. 6 is an example of a display for hands free facility status alertsaccording to one or more embodiments of the present disclosure.

FIG. 7 is an example of a display for hands free facility status alertsaccording to one or more embodiments of the present disclosure.

FIG. 8 is an example of a computing device for hands free facilitystatus alerts according to one or more embodiments of the presentdisclosure.

DETAILED DESCRIPTION

Devices, methods, and systems for hands free facility status alerts aredescribed herein. One system includes a computing device for hands freebuilding automation notifications, comprising a memory and a processorto execute executable instructions stored in the memory to: receive anotification of an event from a building automation system, modify thenotification to include only pre-defined attributes of the notificationthat are displayable on a user interface of a wearable device, andtransmit the modified notification to the wearable device.

The devices, methods, and systems for hands free facility status alertsdescribed herein can be utilized to more efficiently deliver statusinformation of a facility such as an area or building. In some examples,the devices within the facility can be monitored and/or controlled by abuilding automation system. The building automation system can beutilized to send notifications to a plurality of client devices (e.g.,mobile device, computing device, etc.). For example, the buildingautomation system can determine that an event has occurred for aparticular device or system within the facility. In this example, thebuilding automation system can determine that a device is malfunctioningand can send a notification to the plurality of client devices.

In some examples, the building automation system or a platform coupledto the building automation system can modify a notification to includeonly pre-defined attributes of the notification that are displayable ona user interface of a wearable device. For example, the platform canmodify the notification to include: a source, a priority level of thenotification, a category that defines a type of the notification, and/ora brief description of an event that initiated the notification. In someexamples, the user interface can be utilized to receive a selection todisplay categorized data of the notification from an event tablecorresponding to the event.

In some examples, the devices, methods, and systems for hands freefacility status alerts described herein can be utilized to notify a userof a wearable device such that the user can be notified while performingother tasks. For example, the user can be notified of an event detectedby the building automation system while working on a system monitored bythe building automation system. In this example, the event can relate tothe work being performed by the user. In this example, the user canutilize the user interface of the wearable device to transmit a messageto the building automation system updating a status of the event. Inthis example, the building automation system can send updates within thesame event table as the original notification. Thus, the devices,methods, and systems for hands free facility status alerts describedherein can provide real time status updates for events that trigger anotification from the building automation system.

In the following detailed description, reference is made to theaccompanying drawings that form a part hereof. The drawings show by wayof illustration how one or more embodiments of the disclosure may bepracticed.

These embodiments are described in sufficient detail to enable those ofordinary skill in the art to practice one or more embodiments of thisdisclosure. It is to be understood that other embodiments may beutilized and that process changes may be made without departing from thescope of the present disclosure.

As will be appreciated, elements shown in the various embodiments hereincan be added, exchanged, combined, and/or eliminated so as to provide anumber of additional embodiments of the present disclosure. Theproportion and the relative scale of the elements provided in thefigures are intended to illustrate the embodiments of the presentdisclosure, and should not be taken in a limiting sense.

The figures herein follow a numbering convention in which the firstdigit or digits correspond to the drawing figure number and theremaining digits identify an element or component in the drawing.Similar elements or components between different figures may beidentified by the use of similar digits.

FIG. 1 is an example of a system 100 for hands free facility statusalerts according to one or more embodiments of the present disclosure.As shown in FIG. 1, the system 100 includes a platform 102, a buildingautomation system 108, a network 110, and a number of mobile devices112-1, 112-2, 112-N. Platform 102 can include a database 104 andcomputing device 106.

Computing device 106 can receive a notification of an alarm frombuilding automation system 108. For example, computing device 106 canreceive an alarm relating to a fault that may be occurring in buildingautomation system 108. For instance, a fault in a piece of HVACequipment, such as a stuck valve, may be occurring that causes an alarmto be generated and sent to building automation system 108. Computingdevice 106 can send the notification of the alarm to the number ofmobile devices 112-1, 112-2, and/or 112-N via network 110.

As used herein, a fault can include an event that occurs to cause apiece of equipment and/or a control strategy of a building to functionimproperly or to cause abnormal behavior in a building, or a zone of thebuilding, serviced by building automation system 108. In some examples,a fault can include a piece of equipment breaking down. In someexamples, a fault can include a component of a piece of equipmentceasing to function correctly. In some examples, a fault can includeabnormal behavior of a piece of equipment and/or a zone.

Although a fault is described as including equipment breakdowns andabnormal behavior, embodiments of the disclosure are not so limited. Forexample, faults can include any other event that causes equipment orcontrol strategies to function improperly, and/or causes abnormalbehavior to occur in a building serviced by building automation system108.

As used herein, an alarm can include a notification of a fault or event.For example, a fault may be detected by a physical and/or inferentialsensor, where the physical and/or inferential sensor sends a signal tobuilding automation system 108 in response to detection of a fault.Building automation system 108 can generate an alarm to notify a user ofbuilding automation system 108, such as a building owner, buildingmanager, engineer, and/or other personnel.

As shown in FIG. 1, computing device 106 can be included in platform102. Platform 102 can receive notifications of a number of alarms frombuilding automation system 108 via network 110, where platform 102includes computing device 106 and database 104.

Network 110 can be a wired or wireless network that connects buildingautomation system 108, platform 102, and the number of mobile devices112-1, 112-2, 112-N. Examples of such a network relationship can includea local area network (LAN), wide area network (WAN), personal areanetwork (PAN), a distributed computing environment (e.g., a cloudcomputing environment), storage area network (SAN), Metropolitan areanetwork (MAN), a cellular communications network, and/or the Internet,among other types of network relationships.

In some examples, the platform 102 can be utilized to modifynotifications received from the building automation system 108. Forexample, the platform 102 can utilize the computing device 106 to modifythe notification to include only pre-defined attributes of thenotification that are displayable on a user interface of a wearabledevice. In some examples, the building automation system 108 can modifythe generated notifications to include only pre-defined attributes ofthe notification that are displayable on the user interface of thewearable device. For example, the building automation system 108 canhave a direct communication channel with the mobile devices 112-1,112-2, 112-N to send the modified notifications to the mobile devices112-1, 112-2, 112-N.

In some examples, the mobile devices 112-1, 112-2, 112-N can be wearabledevices. In some examples, a wearable device can include a device thatcan be worn by a user. In some examples, the wearable device can beattached to a user such that the user can utilize both hands while thewearable device is attached to the user. In some examples, the wearabledevice can be attached via a physical strap or pin that can attach thewearable device to the user. In some examples, the wearable device caninclude, but is not limited to: a smartwatch, a pin, an arm band, awrist band, among other devices that can be worn by the user. In someexamples, the wearable device can include a processor, memory withinstructions that can be executed by the processor, and/or a userinterface as described herein.

In some examples, the mobile devices 112-1, 112-2, 112-N or wearabledevices can utilize a number of signals to notify a user when anotification is received. For example, the wearable devices can utilizea sound notification to notify a user that a notification was receivedfrom the platform or building automation system. In some examples, thewearable devices can utilize a haptic notification to notify a user whena notification is received. For example, the wearable devices canvibrate to notify a user that a notification was received from theplatform 102 or building automation system 108. In some examples, thewearable devices can display a light (e.g., color coded light, coloredlight emitting diode, etc.) to notify a user that a notification wasreceived from the platform 102 or building automation system 108.

In some examples, the platform 102 can be utilized to transmit themodified notification to the wearable device and/or the mobile devices112-1, 112-2, 112-N. In some examples, the platform 102 can determine aportion of the mobile devices 112-1, 112-2, 112-N to transmit themodified notification. For example, the platform 102 can determine anumber of users that have a relationship to the notification and sendthe modified notification to mobile devices 112-1, 112-2, 112-N thatcorrespond to the number of users. For example, the notification canrelate to an event such as a measured flow of a heater being above orbelow a threshold value. In this example, the platform 102 can determinea number of users that are related to the HVAC system, the heatingsystem, the heater, and/or the pump corresponding to the heater. In someexamples, technicians and managers that are responsible for maintainingor installing the HVAC system can be sent the notification while otherusers that may not be involved with maintaining or installing the HVACsystem are not sent the notification.

In some examples, the mobile devices 112-1, 112-2, 112-N can be wearabledevices with a relatively smaller user interface surface compared toother mobile devices (e.g., cell phone, laptop, tablet, etc.). In theseexamples, the platform 102 can modify a notification received from thebuilding automation system 108 to fit within the relatively smaller userinterface surface. For example, the platform 102 can modify thenotification to include only pre-defined attributes of the notificationthat are displayable on a user interface of a wearable device.

The pre-defined attributes can provide sufficient information to a usersuch that the user can identify a source of the notification, identify apriority level of the notification, identify a category of thenotification, and/or identify a brief description of the notification onthe user interface of the wearable device. In some examples, thepre-defined attributes can include a source of the event notificationthat defines an issue (e.g., event, fault, etc.) detected by thebuilding automation system. In some examples, the source of the eventcan include a description of the issue that fits within the userinterface of the wearable device. For example, code or short handdescription can be utilized to describe a physical location and/orphysical device that is associated with the event. In some examples, theevent can be triggered by sensor data associated with a physical deviceand the source can include a description and/or location of the physicaldevice.

In some examples, the pre-defined attributes can include a prioritylevel corresponding to the notification. In some examples, the prioritylevel corresponding to the notification can include a pre-definedpriority level based on an urgency of the event associated with thenotification. For example, the priority level can be based on howimportant it is to respond to the notification in a timely manner. Inthis example, a higher priority level (e.g., a more important event,etc.) can correspond to an event where a faster response time isrequired. For example, the event can be a device failure. In thisexample, the device failure may cause damage to other devices or otherobjects within the area. In this example, the event can have arelatively higher priority level since a faster response time can savecosts or prevent potential damage to other objects or devices within thefacility. Similarly, a lower priority level (e.g., less important event,etc.) can correspond to an event that may not require a fast responsetime, but may be an event that indicates a particular device or area mayneed maintenance at some point to prevent a failure.

In some examples, the pre-defined attributes can include a category thatdefines a type of the notification. In some examples, the category candefine whether the notification corresponds to a device failure, amaintenance reminder, a project update, and/or other type ofnotification. In some examples, the category can be utilized todetermine a number of users to receive the notification. For example,the category of the notification can define particular skill sets thatmay be useful in responding to the event. In some examples, the categorycan be utilized to identify a type of response requested from the userof the wearable device. For example, the category can help a manageridentify other users to contact for technical support. In this example,the category can help a technician determine what type of equipment maybe needed to respond to the event.

In some examples, the pre-defined attributes can include trendinformation that defines data over a period of time corresponding to thenotification. In some examples, the trend information can include sensordata collected by the building automation system 108 for a device orarea associated with the event. In some examples, the trend informationcan be utilized to identify why the building automation system 108transmitted a notification to the platform 102. In some examples, thetrend information is displayable as a graphical representation. Forexample, the sensor data can include temperature data for a heater. Inthis example, the graphical representation can include temperature datacollected by sensors over a period of time.

In some examples, the platform 102 can receive feedback from the userinterface of the wearable device or the mobile devices 112-1, 112-2,112-N. In some examples, the platform 102 can upload the feedback to thebuilding automation system 108. In some examples, the feedback can begenerated utilizing a text message or voice message converted to a textmessage.

In some examples, the feedback can be a snooze or close selection asdescribed herein. For example, the platform 102 can receive a snoozeindication from the user interface of the wearable device to delayfurther notifications relating to the event. In this example, thenotification can be displayed in an event table where multiple differentnotifications can be categorized or organized. In some examples, thesnooze indication can include a time period to define a quantity of timeto block additional notifications that relate to similar events thatinitiated the original notification. In some examples, the feedback caninclude a response to the notification to update other users or othermobile devices 112-1, 112-2, 112-N.

In some examples, the platform 102 can receive the feedback from thewearable device and transmit the feedback to the building automationsystem 108. For example, the platform 102 can update the buildingautomation system 108 with the feedback provided by a number ofdifferent users. In this example, the updates to the building automationsystem 108 can be utilized to send additional notifications relating tothe event back to the platform 102. In this example, the platform 102can modify the updated notifications as described herein to be displayedon the user interface of a wearable device.

The system 100 as described herein can be utilized to provide hands freenotifications to a plurality of users associated with a buildingautomation system 108. The notifications from the building automationsystem 108 can be modified by the platform 102 to provide just enoughinformation to assess the source and urgency of an event associated withthe notification. The system 100 can also provide a user with the optionto provide feedback to the notification. As described herein, thefeedback can provide additional information or additional directions forresponding to the event. Thus, the system 100 can provide real timestatus information for a number of events monitored and/or controlled bythe building automation system 108 on a user interface of a wearabledevice.

FIG. 2 is an example of a display 220 for hands free facility statusalerts according to one or more embodiments of the present disclosure.In some examples, the display 220 can be a user interface of a wearabledevice. For example, the display 220 can be a user interface of a smartwatch that utilizes a computing device to provide the functionsdescribed herein.

In some examples, the display 220 can be relatively smaller in sizecompared to other mobile devices. In some examples, the display 220 caninclude an event table that includes a plurality of notifications 222-1,222-2 that each correspond to a different event. Within eachnotification 222-1, 222-2 there can be a number of pre-definedattributes 224. For example, the notification 222-1 can include a numberof pre-defined attributes 224-1, 224-2, 224-3, 224-3, 224-4, 224-5,224-6 that each provide pre-defined information associated with thenotification 222-1.

In some examples, the pre-defined attributes 224 can include a sourceattribute 224-1 to define a source of the notification 222-1. In someexamples, the source attribute 224-1 can provide a brief description ofthe issue detected by a building automation system. In some examples,the source attribute 224-1 can identify a general type of issuedetected. In some examples, the pre-defined attributes 224 can include apriority level attribute 224-2. As described herein, the priority levelattribute 224-2 can define an importance of responding to the eventassociated with the notification 222-1. In some examples, the prioritylevel attribute 224-2 can indicate a suggested time period forresponding to the event associated with the notification 222-1.

In some examples, the pre-defined attributes 224 can include a categoryattribute 224-3. In some examples, the category attribute 224-3 canidentify a type of notification and/or a type of event that triggeredthe notification 222-1. For example, the category attribute 224-3 caninclude a description of the device that is associated with the eventand/or the sensor that triggered the event.

In some examples, the pre-defined attributes 224 can include a conditionattribute 224-4 that can indicate real time data corresponding to theevent. In some examples, the condition attribute 224-4 can include avalue detected by the sensor and/or device as described herein. Forexample, the condition attribute 224-4 can include a flow rate detectedby a sensor coupled to a heater or chiller.

In some examples, the pre-defined attributes 224 can include adescription attribute 224-5 that can include a brief description of theevent and/or a brief description of why the notification 222-1 wastransmitted to the platform from the building automation system. Forexample, the description attribute 224-5 can describe that a pump orflow rate to a heater is above or below a threshold value.

In some examples, the pre-defined attributes 224 can include a timestampattribute 224-6. In some examples, the timestamp attribute 224-6 can bea date and time that an event or alarm was determined by the buildingautomation system. In some examples, the timestamp attribute 224-6 caninclude a date and time that the notification 222-1 was sent by theplatform. In some examples, the timestamp attribute 224-6 can include aquantity of time since the notification 222-1 was received at thewearable device. In some examples, the timestamp attribute 224-6 canindicate a date and time of an update to the notification 222-1 and/orindicate a quantity of time since the most recent update to thenotification 222-1.

FIG. 3 is an example of a display 320 for hands free facility statusalerts according to one or more embodiments of the present disclosure.In some examples, the display 320 can be displayed on a user interfaceof the same or similar user interface of a wearable device as describedherein. In some examples, the display 320 can include a notification 322with corresponding pre-defined attributes 324. In some examples, thedisplay 320 can also include an update selection tool 326. In someexamples, selecting the update selection tool 326 can display a numberof update attributes 328.

In some examples, the update attributes 328 can include a number ofselectable attributes 328-1, 328-2, 328-3, 328-4. In some examples, theupdate attributes 328 can include a selectable snooze attribute 328-1.As described herein, the selectable snooze attribute 328-1 can delayadditional notifications relating to the notification 322 for a periodof time. In some examples, the snooze attribute 328-1 can include anoption to select the period of time to delay additional notifications.That is, the snooze attribute can include a time period to define aquantity of time to block notifications relating to the notification322.

In some examples, the update attributes 328 can include a selectableflag attribute 328-2. In some examples, the selectable flag attribute328-2 can generate a flag for the notification 322. In some examples,the flag can be used to organize a plurality of notifications includingthe notification 322. In some examples, the flag can allow a user toidentify the notification 322 from a plurality of notifications.

In some examples, the update attributes 328 can include a selectableclose attribute 328-3. In some examples, the selectable close attribute328-3 can be selected to close the notification 322 and/or delete thenotification from an event table that includes a plurality ofnotifications including the notification 322. In some examples, theselectable close notification can be utilized to organize notificationswithin the event table by removing notifications that have beenaddressed and/or are no longer applicable for a particular user.

In some examples, the update attributes 328 can include a selectablecomment attribute 328-4. In some examples, the selectable commentattribute 328-4 can be utilized to generate a comment or messagecorresponding to the notification 322. In some examples, the selectablecomment attribute 328-4 can be utilized to generate feedback in responseto the notification 322. In some examples, the generated message orfeedback can be transmitted to the platform and/or the buildingautomation system. In some examples, the message or feedback can bedistributed to other wearable devices when the building automationsystem is updated. In some examples, the message or feedback can beutilized to instruct other users how to respond to the notification 322.

FIG. 4 is an example of a display 420 for hands free facility statusalerts according to one or more embodiments of the present disclosure.In some examples, the display 420 can be displayed on the same orsimilar user interface of a wearable device as described herein. In someexamples, the display 420 can include a notification 422 withcorresponding pre-defined attributes 424. In some examples, thenotification 422 can include a new activity tab 430.

In some examples, the new activity tab 430 can include updatesassociated with the notification 422. As described herein, a number ofusers can provide messages and/or updates for the notification 422. Insome examples, the new activity tab 430 can be a selectable tab todisplay the messages and/or the updates when selected. As describedherein, the messages and/or the updates can be snoozed when a snoozeselectable attribute is selected.

FIG. 5 is an example of a display 520 for hands free facility statusalerts according to one or more embodiments of the present disclosure.In some examples, the display 520 can be displayed on the same orsimilar user interface of a wearable device as described herein. In someexamples, the display 520 can include a notification 522 withcorresponding pre-defined attributes 524.

In some examples, the display 520 can include a modified notificationthat includes a graphical representation 536 of the event over a periodof time. As described herein, the graphical representation 536 caninclude sensor data for a particular device or area that corresponds tothe event. For example, the sensor data can include temperature readingsof a heater or cooling device over a period of time. The graphicalrepresentation 536 can be utilized to determine how the sensor dataresulted in the event identified by the building automation system.

In some examples, the display 520 can include a selectable commentattribute 532 and/or a selectable menu attribute 534. In some examples,the comment attribute 532 can be utilized to generate a message and/orfeedback as described herein. In some examples, the comment attribute532 can be utilized to generate a message and/or feedback in response tothe graphical representation 536. In some examples, the selectable menuattribute 534 can be utilized to display other selectable attributes asdescribed herein. In some examples, the comment attribute 532 can beutilized to send a message or feedback directly to a different mobiledevice or wearable device.

FIG. 6 is an example of a display 620 for hands free facility statusalerts according to one or more embodiments of the present disclosure.In some examples, the display 620 can be displayed on the same orsimilar user interface of a wearable device as described herein. In someexamples, the display 620 can include a notification with correspondingpre-defined attributes. In some examples, the display 620 can include anumber of messages 638 corresponding to the notification.

In some examples, the display 620 can include a selectable commentattribute 632 and/or a selectable menu attribute 634 as describedherein. In some examples, the comment attribute 632 can be utilized togenerate a message to respond to the number of messages 638. In someexamples, the display 620 can include a selectable comment attribute 628for updating the building automation system as described herein.

FIG. 7 is an example of a display 720 for hands free facility statusalerts according to one or more embodiments of the present disclosure.In some examples, the display 720 can be displayed on the same orsimilar user interface of a wearable device as described herein. In someexamples, the display 720 can include a notification with correspondingpre-defined attributes. In some examples the pre-defined attributes canbe displayed as a selectable snooze attribute 744, a selectable flagattribute 740, a selectable close attribute 746, and/or a selectablecomment attribute 742.

FIG. 8 is an example of a computing device 890 for multi-usercommissioning according to one or more embodiments of the presentdisclosure. Computing device 890 can be, for example, a commodityserver, a data center that comprises a plurality of servers, among othertypes of computing devices or embedded system. Computing device 890 canbe utilized in system 100, displays 220, 320, 420, 520, 620, 720, and/ormethods described herein to perform the functions previously describedherein. For example, computing device 890 can be included in a mobiledevice such as mobile computing device 112 as referenced in FIG. 1.

As shown in FIG. 8, computing device 890 includes a memory 892 and aprocessing resource 894 (e.g., processor) coupled to memory 892. Memory892 can be any type of storage medium that can be accessed by processingresource 894 to perform various examples of the present disclosure. Forexample, memory 892 can be a non-transitory computer readable mediumhaving computer readable instructions (e.g., computer programinstructions) stored thereon that are executable by processing resource894 to perform localizing a fault on a live cable in accordance with oneor more embodiments of the present disclosure.

Memory 892 can be volatile or nonvolatile memory. Memory 892 can also beremovable (e.g., portable) memory, or non-removable (e.g., internal)memory. For example, memory 892 can be random access memory (RAM) (e.g.,dynamic random access memory (DRAM) and/or phase change random accessmemory (PCRAM)), read-only memory (ROM) (e.g., electrically erasableprogrammable read-only memory (EEPROM) and/or compact-disc read-onlymemory (CD-ROM)), flash memory, a laser disc, a digital versatile disc(DVD) or other optical disk storage, and/or a magnetic medium such asmagnetic cassettes, tapes, or disks, among other types of memory.

Further, although memory 892 is illustrated as being located incomputing device 890, embodiments of the present disclosure are not solimited. For example, memory 892 can also be located internal to anothercomputing resource (e.g., enabling computer readable instructions to bedownloaded over the Internet or another wired or wireless connection).

As shown in FIG. 8, computing device 890 can also include a userinterface 896. User interface 896 can include, for example, a display(e.g., a screen). The display can be, for instance, a touch-screen(e.g., the display can include touch-screen capabilities). Userinterface 896 (e.g., the display of user interface 896) can provide(e.g., display and/or present) information to a user of computing device890. In some examples, the user interface 896 can be a user interface ofa wearable device.

Additionally, computing device 890 can receive information from the userof computing device 890 through an interaction with the user via userinterface 896. For example, computing device 890 (e.g., the display ofuser interface 896) can receive input from the user via user interface896. The user can enter the input into computing device 890 using, forinstance, a mouse and/or keyboard associated with computing device 890,or by touching the display of user interface 896 in embodiments in whichthe display includes touch-screen capabilities (e.g., embodiments inwhich the display is a touch screen).

As used herein, “a” or “a number of” something can refer to one or moresuch things. For example, “a number of resources” can refer to one ormore resources. Additionally, the designator “N”, as used herein,particularly with respect to reference numerals in the drawings,indicates that a number of the particular feature so designated can beincluded with a number of embodiments of the present disclosure.

As described herein, a “module” can include computer readableinstructions that can be executed by a processing resource to perform aparticular function. A module can also include hardware, firmware,and/or logic that can perform a particular function.

As used herein, “logic” is an alternative or additional processingresource to execute the actions and/or functions, described herein,which includes hardware (e.g., various forms of transistor logic,application specific integrated circuits (ASICs)), as opposed tocomputer executable instructions (e.g., software, firmware) stored inmemory and executable by a processing resource.

Although specific embodiments have been illustrated and describedherein, those of ordinary skill in the art will appreciate that anyarrangement calculated to achieve the same techniques can be substitutedfor the specific embodiments shown. This disclosure is intended to coverany and all adaptations or variations of various embodiments of thedisclosure.

It is to be understood that the above description has been made in anillustrative fashion, and not a restrictive one. Combination of theabove embodiments, and other embodiments not specifically describedherein will be apparent to those of skill in the art upon reviewing theabove description.

The scope of the various embodiments of the disclosure includes anyother applications in which the above elements and methods are used.Therefore, the scope of various embodiments of the disclosure should bedetermined with reference to the appended claims, along with the fullrange of equivalents to which such claims are entitled.

In the foregoing Detailed Description, various features are groupedtogether in example embodiments illustrated in the figures for thepurpose of streamlining the disclosure. This method of disclosure is notto be interpreted as reflecting an intention that the embodiments of thedisclosure require more features than are expressly recited in eachclaim.

Rather, as the following claims reflect, inventive subject matter liesin less than all features of a single disclosed embodiment. Thus, thefollowing claims are hereby incorporated into the Detailed Description,with each claim standing on its own as a separate embodiment.

What is claimed is:
 1. A computing device for interfacing buildingautomation notifications with a mobile device, the computing devicecomprising a memory and a processor to execute executable instructionsstored in the memory to: receive an input building automationnotification of an event from a building automation system, the receivedinput building automation notification having a plurality of attributesrelated to the event; provide an output building automation notificationthat includes only pre-defined ones of the plurality of attributes ofthe input building automation notification, wherein the pre-defined onesinclude less than all of the plurality of attributes of the inputbuilding automation notification; transmit the output buildingautomation notification to the mobile device for alerting a user of theevent; receive user input transmitted by the mobile device that includesan input from the user of the mobile device for responding to the event;and in response to receiving the user input from the mobile device,notify the building automation system of the received user input.
 2. Thecomputing device of claim 1, wherein one of the pre-defined ones of theplurality of attributes provided in the output building automationnotification includes an event description attribute that includes adescription of a device of the building automation system that isassociated with the event and/or a description of a sensor thattriggered the event.
 3. The computing device of claim 1, wherein theprocessor executes executable instructions stored in the memory to:provide a code or short hand description for at least one of thepredefined attributes in the output building automation notification,wherein the code or short hand description is configured to fit on adisplay of the mobile device.
 4. The computing device of claim 3,wherein one of the plurality of attributes in the received inputbuilding automation notification includes an event description attributethat includes a description of a device of the building automationsystem that is associated with the event and/or a description of asensor that triggered the event, and wherein one of the pre-defined onesof the plurality of attributes provided in the output buildingautomation notification includes an event description attribute thatincludes a code or short hand description of the description containedin the event description attribute of the received input buildingautomation notification.
 5. The computing device of claim 1, wherein theprocessor executes executable instructions stored in the memory to: inresponse to notifying the building automation system of the receiveduser input, receive an update from the building automation system; andtransmit the update to the mobile device for alerting a user of theupdate.
 6. The computing device of claim 5, wherein the update from thebuilding automation system comprises an updated building automationnotification that includes a plurality of updated attributes, andwherein the processor executes executable instructions stored in thememory to: provide an updated output building automation notificationthat includes only pre-defined ones of the plurality of updatedattributes of the updated building automation notification, wherein thepre-defined ones of the plurality of updated attributes of the updatedbuilding automation notification include less than all of the pluralityof updated attributes of the update building automation notification;and transmit the updated output building automation notification to themobile device.
 7. The computing device of claim 1, wherein the eventcorresponds to a fault or alarm of the building automation system. 8.The computing device of claim 1, wherein the received user inputtransmitted from the mobile device includes a short message service(SMS) text message.
 9. The computing device of claim 1, wherein thepre-defined attributes of the input building automation notificationinclude a source attribute that defines a source of the event.
 10. Thecomputing device of claim 1, wherein the pre-defined attributes of theinput building automation notification include a priority attribute thatdefines a priority level of the event.
 11. The computing device of claim1, wherein the pre-defined attributes of the input building automationnotification include a category attribute that defines a type of theevent.
 12. The computing device of claim 1, wherein the pre-definedattributes of the input building automation notification include a trendattribute that trend associated with the event.
 13. The computing deviceof claim 1, wherein at least one of the pre-defined attributes of theoutput building automation notification is abbreviated relative to thecorresponding one of the plurality of attributes of the input buildingautomation notification.
 14. The computing device of claim 1, whereinthe processor executes executable instructions stored in the memory to:receive a snooze indication from the mobile device; and in response toreceiving the snooze indication, stop sending further output buildingautomation notification regarding the event for at least a snooze periodof time.
 15. A method for interfacing building automation notificationswith a mobile device, the method comprising: receiving an input buildingautomation notification of an event from a building automation system,the received input building automation notification having a pluralityof attributes related to the event; providing an output buildingautomation notification that includes only pre-defined ones of theplurality of attributes of the input building automation notification,wherein the pre-defined ones include less than all of the plurality ofattributes of the input building automation notification; abbreviatingat least one of the pre-defined attributes of the output buildingautomation notification relative to the corresponding one of theplurality of attributes of the input building automation notification;transmit the output building automation notification to the mobiledevice for alerting a user of the event; receive user input transmittedby the mobile device that includes an input from the user of the mobiledevice for responding to the event; and notify the building automationsystem of the received user input.
 16. The method of claim 15, whereinthe received user input includes one of a plurality of predefinedresponses.
 17. The method of claim 16, wherein the plurality ofpredefined responses comprises a snooze response, wherein in response toreceiving the snooze response, further output building automationnotification regarding the event are stopped for at least a snoozeperiod of time.
 18. A mobile device for managing building automationnotifications of a building automation system, the mobile devicecomprising: a user interface; a memory; and a processor configured toexecute executable instructions stored in the memory to: receive anotification of an event detected by the building automation system, thereceived notification includes a plurality of condensed attributesrelated to attributes of a corresponding building automationnotification provided by the building automation system, wherein theplurality of condensed attributes include less than all of theattributes of the corresponding building automation notificationprovided by the building automation system and at least one of theattributes is abbreviated relative to a corresponding attribute of thecorresponding building automation notification provided by the buildingautomation system; display the received notification on the userinterface of the mobile device; receive feedback by selecting, via theuser interface of the mobile device, one of a plurality of predeterminedresponses for responding to the event; and send the feedback to a remotedevice.
 19. The mobile device of claim 18, wherein the one of theplurality of predetermined responses comprises one of a selection tosnooze additional notifications relating to the event and a selection togenerate a message to include within an event table.
 20. The mobiledevice of claim 18, wherein the plurality of predetermined responses aredisplayed on the user interface.